home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c,comp.lang.c++,alt.2600
- Subject: Re: Need info on virus source code
- Date: 9 Feb 1996 21:46:36 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4fhbfsINN8t2@keats.ugrad.cs.ubc.ca>
- References: <4f1gqa$gnt$2@mhadf.production.compuserve.com> <4f2m0eINNm17@keats.ugrad.cs.ubc.ca> <4f6g8h$hs4@dfw.nkn.net>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <4f6g8h$hs4@dfw.nkn.net>, <TheAnalyst@Nfo.Org> wrote:
- >c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku) wrote:
- >
- >>In article <4f1gqa$gnt$2@mhadf.production.compuserve.com>,
- >>dpmullin@ix.netcom.com <75604.20@CompuServe.COM> wrote:
- >>>Hello out there
- >>>
- >>>Is there any way to obtain virus source code?
- >
- >>I once wrote a virus whose (assembly language) source code was heavily
- >>commmented, and was accompanied by detailed internal documentation.
- >
- >>It is sitting on a 20MB Seagate hard drive in a junk yard somewhere.
- >
- >>I never realeased it because it could have been exploited by the unworthy to do
- >>harm.
- >
- >Give me a break. It is a very bad idea to cross post alt.2600 to any other
- >group. I bet you didn't even write a true virus, probably just another fancy
- >trojan that most people call viruses.
-
- Nope. Self-replicating piece of machine code spreading through executable
- files, with some rudimentary self-encryption.
-
- I didn't do anything fancy like permuting sequences of instructions, though if
- I were to do it again, I would include mutation for sure. I did have a
- self-comparison test that would tell the virus whether a program was already
- infected with itself, plus certain criteria checks for suitable "hosts".
-
- It was not difficult to produce, in comparison with a real software project,
- like say a compiler or operating system. Just several afternoons' worth of
- pleasant diversion.
- --
-
-